Fix PEKA input mismatch by joining peaks and crosslinks on metadata#34
Merged
CharlotteAnne merged 1 commit intogoodwright:masterfrom Jul 14, 2025
Merged
Fix PEKA input mismatch by joining peaks and crosslinks on metadata#34CharlotteAnne merged 1 commit intogoodwright:masterfrom
CharlotteAnne merged 1 commit intogoodwright:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses Issue #33, where PEKA runs are using unmatched peak and crosslink files across samples.
The problem was caused by CLIPPY_GENOME.out.peaks and ch_genome_crosslink_bed being passed separately to the PEKA module without matching on sample metadata.
This fix joins the two channels by metadata using .join(..., by: 0) and maps them into the PEKA process, ensuring proper sample pairing.